Troubleshooting purchase order email notifications

This checks that you can send emails using the E-mail settings you have entered.

Open: System Administration > Messaging > E-Mail Settings.

1. Click Edit.

2. Enter an email address in the Send E-Mail To box, and click Send.

   An email is sent to the address specified.

Check your email server settings in System Administration.

Open: System Administration > Messaging > E-Mail Settings.

1. Click Edit.
2. Check your Server Port Number.

3. Check you have selected Server requires secure connection (SSL), if this is required by your mail server.

Sage 200 uses your email address and password to authenticate you with your email server. We use that user name and password to send email through the configured email account. Your password is encrypted when it's stored in the database.

Some internet mail (SMTP) providers require additional security when an email and password is used as authentication which we may not support. To use this email address, you may need change the configuration of your account with your email provider. We recommend that you carefully consider any security recommendations from your email provider.

For Microsoft 365, you should enable the Authenticated SMTP setting (also called SMTP AUTH) for the email account that you use to send notifications. For details on how to do this, see the Microsoft 365 documentation.

We recommend that you:

• Setup a dedicated email account to send and receive the notifications.

• Enable the secure connection setting in Sage 200 to ensure that HTTPS is used.

  Open: System Administration > Messaging > E-Mail Settings.

  1. Click Edit.

  2. Select Server requires secure connection (SSL).

Sometimes your anti-virus software will block the notifications email via your server. Check your anti-virus software settings.

Open: System Administration > Messaging > Purchase Order Authorisation.

1. Click Edit.
2. Select Use Email Notifications.
3. Click OK.

Check the Sage 200 user account Properties.

You can check the log files for more information.

In your Sage 200 application, you can specify another Sage 200 account as an alternative authoriser. This alternative Sage 200 user will receive the notification messages for the original Sage 200 user.

Open: Purchase Order Processing > POP Utilities > System Set Up > Maintain Alternative Authorisers.

• Check if the Sage 200 user has an Alternative set up.

Sage 200 records information about where the service is failing in the Sage 200 Services log file.

To check the Sage 200 Services:

1. To make sure the log file contains more detailed information, open the following file using the Notepad application: C:\Inetpub\Sage 200 App Services\Sage200Services\Web.config.

2. Change the <level value> in the <log4net> section to Debug. This is set to warn by default. For example:

   <log4net>
   <logger name="ApplicationLog">
   <level value="Debug" />
   <appender-ref ref="LogFileAppender" />
   </logger>

   The log file will now contain more detailed information.

   On some systems, due to security constraints, you may also need to create an Empty.log file. The Windows user account the web service runs under also needs permission to write to the log file and the Empty.log file.

3. To check the details of any errors in the log file, open the following file: C:\Inetpub\Sage 200 App Services\Sage200Services\Log\Sage200Services.log